| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CPS.3.11.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.3.11 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CPS_3_11_Support_Other_Encounter_and_Episode_of_Care_Documentation |
| Title | CPS.3.11 Support Other Encounter and Episode of Care Documentation (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Where not covered above, provide the means to manage and organize the documentation of the health care needed and delivered during an encounter/episode of care. |
| Purpose | Using data standards and technologies that support interoperability, effective documentation of an encounter can promote patient- centered/oriented care and enables real-time, immediate point-of-service care delivery. Effective encounter and episode-of-care documentation can facilitate efficient work flow and improve operations performance. This can help to ensure the integrity of - the health record, - public health, financial and administrative reporting, and - the healthcare delivery process. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Where not covered above, provide the means to manage and organize the documentation of the health care needed and delivered during an encounter/episode of care.
Using data standards and technologies that support interoperability, effective documentation of an encounter can promote patient- centered/oriented care and enables real-time, immediate point-of-service care delivery. Effective encounter and episode-of-care documentation can facilitate efficient work flow and improve operations performance. This can help to ensure the integrity of
| CPS.3.11#01 | SHALL |
The system SHALL provide the ability to render patient data by encounter, including previous admissions and episodes of care. |
| CPS.3.11#02 | SHOULD |
The system SHOULD provide the ability to capture and annotate patient encounter data from external systems, such as diagnostic tests and reports. |
| CPS.3.11#03 | SHALL |
The system SHALL provide the ability to capture encounter documentation by one or more of the following input methods:
|
| CPS.3.11#04 | SHOULD |
The system SHOULD provide the ability to capture and maintain presentation filters that are specific to the types of encounter (e.g., care provider specialty, location of encounter, date of encounter, associated diagnosis). |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CPS.3.11",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Where not covered above, provide the means to manage and organize the documentation of the health care needed and delivered during an encounter/episode of care.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Using data standards and technologies that support interoperability, effective documentation of an encounter can promote patient- centered/oriented care and enables real-time, immediate point-of-service care delivery. Effective encounter and episode-of-care documentation can facilitate efficient work flow and improve operations performance. This can help to ensure the integrity of</p>\n<ul>\n<li>the health record,</li>\n<li>public health, financial and administrative reporting, and</li>\n<li>the healthcare delivery process.</li>\n</ul>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.11#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render patient data by encounter, including previous admissions and episodes of care.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.11#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and annotate patient encounter data from external systems, such as diagnostic tests and reports.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.11#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture encounter documentation by one or more of the following input methods:</p>\n<ul>\n<li>direct keyboard entry of text;</li>\n<li>structured data entry utilizing templates, forms, pick lists or macro substitution; and</li>\n<li>dictation with subsequent transcription of voice to text, either manually or via voice recognition system.</li>\n</ul>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.3.11#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain presentation filters that are specific to the types of encounter (e.g., care provider specialty, location of encounter, date of encounter, associated diagnosis).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.3.11",
"version" : "2.1.0",
"name" : "CPS_3_11_Support_Other_Encounter_and_Episode_of_Care_Documentation",
"title" : "CPS.3.11 Support Other Encounter and Episode of Care Documentation (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Where not covered above, provide the means to manage and organize the documentation of the health care needed and delivered during an encounter/episode of care.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Using data standards and technologies that support interoperability, effective documentation of an encounter can promote patient- centered/oriented care and enables real-time, immediate point-of-service care delivery. Effective encounter and episode-of-care documentation can facilitate efficient work flow and improve operations performance. This can help to ensure the integrity of \n- the health record, \n- public health, financial and administrative reporting, and \n- the healthcare delivery process.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.11-01",
"label" : "CPS.3.11#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render patient data by encounter, including previous admissions and episodes of care.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.1.5#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.11-02",
"label" : "CPS.3.11#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and annotate patient encounter data from external systems, such as diagnostic tests and reports.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.1.5#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.11-03",
"label" : "CPS.3.11#03",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture encounter documentation by one or more of the following input methods:\n- direct keyboard entry of text;\n- structured data entry utilizing templates, forms, pick lists or macro substitution; and\n- dictation with subsequent transcription of voice to text, either manually or via voice recognition system.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.1.5#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.3.11-04",
"label" : "CPS.3.11#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain presentation filters that are specific to the types of encounter (e.g., care provider specialty, location of encounter, date of encounter, associated diagnosis).",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.1.5#4"
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.